Fixes ordering for loaded events by API #81
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses an issue regarding the ordering of events after a page reload. Initially, all requested events are correctly fetched in descending order. However, a discrepancy arises when the frontend adds new events to the local store. Instead of inserting new events at the beginning of the array, which would maintain the descending order, they are appended to the end. This fix ensures that new events are correctly placed at the start of the array.
fixes #80